-
Notifications
You must be signed in to change notification settings - Fork 196
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(store-sync,store-indexer): make last updated block number not null #1972
Conversation
🦋 Changeset detectedLatest commit: fe69511 The changes in this PR will be included in the next version bump. This PR includes changesets to release 30 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
@@ -53,7 +53,8 @@ export async function getLogs( | |||
const records = await database | |||
.select() | |||
.from(tables.recordsTable) | |||
.where(or(...conditions)); | |||
.where(or(...conditions)) | |||
.orderBy(asc(tables.recordsTable.lastUpdatedBlockNumber)); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
originally had this as
.orderBy(sql`${tables.recordsTable.lastUpdatedBlockNumber} ASC NULLS FIRST`)
but then realize there's ~no case where we'd add records to the table without a block number (both RPC and another indexer will provide this info)
so I decided to make these fields not nullable
following up #1965
not strictly a bug but just doing this for completeness so we don't have to sort inline